Peer Connections Page Actions
The Peer Connections page (Network > Peer Connections) allows operators to view the Peer Connections in the IP telephony network. The maximum number of allowed Peer Connections in the ARM is 30000. This number is enforced; an alarm is generated if the threshold is crossed, and new Peer Connections are not allowed to be added to the ARM.
The following information on each Peer Connection is displayed:
The information displayed in the Peer Connections page is identical to that displayed in the Network Map page described under Peer Connection Information and Actions. You can search for the name of a node associated with the Peer Connection, the name of a Peer Connection, or a VoIP Peer name. It's useful to find, for example, all Peer Connections of a specific node.
Use the buttons in the Peer Connections page to perform the following actions:
|
■
|
Sync Topology available from the Actions drop-down. |
|
■
|
Delete after selecting the row of the Peer Connection to delete. Note that the Delete option is displayed only for Peer Connections in locked and pre-deleted state, unassociated with routing rules or with a Policy Studio rule. for related information, see under Peer Connection Information and Actions. |
In addition to Lock / Unlock of a Peer Connection, you can select a directional basedLock / Unlock. This feature allows you to (for example) stop only traffic towards a specific VoIP Peer (for example, a specific IVR) while calls coming from this VoIP Peer will still be routed to their destination. You can use the feature to perform a graceful stoppage of traffic for maintenance reasons (for example).
The feature is essential for IVR VoIP Peers when there are always calls in a queue that are not yet connected to an agent. From the IVR’s perspective, the connection to the agent is outbound calls; without the uni-directional lock feature, calls fail.
The directional lock of a Peer Connection is indicated in Map page and in the Peer Connections page.
|
●
|
A lock of the opposite direction automatically unlocks the previous lock direction; it doesn’t apply a bi-directional lock; it allows traffic of the previously locked direction. Either direction is applicable.
|
|
●
|
The Offline Planning page (Network > Offline Planning) as well as the Test Route feature support direction-based lock. In the example shown in the figure below, Test Route is activated (and allowed) for outgoing calls even though the Peer Connection is locked for incoming calls.
|
Test Route Activated for Outgoing Calls even though the Peer Connection is Locked for Incoming Calls
 for outgoing calls even though the Peer Connection is locked for incoming calls.png)
|
●
|
Multiple rows can be selected; multiple actions (delete, lock/unlock, etc.) are supported. |